home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
os2
/
gigo0714.zip
/
SPEED.FAQ
< prev
next >
Wrap
Text File
|
1996-07-14
|
4KB
|
81 lines
07/14/96: New speedup option: Look for "FASTLOOKUP" below!
Q: How can I speed GIGO up?
A: Things you can do to speed GIGO up:
o Usage of INCLUDE statements is discouraged, as it takes longer to
locate and read in all of your INCLUDE'd segments. Placing everything
into one config file will help speed things up for you.
o Disable on the logging that you don't need. If you have problems,
re-enable the logging that is appropriate for the job at hand.
Logging _really_ slows things down. Don't forget that you have
multiple log files to play with..
o Cut down on the KEEP, KILL, and HIDE statements -
only use what you need. (Affects _every_ message!)
o If you don't need the FIDOECHOS functionality, comment
it out. Saves memory, and saves time converting newsgroups.
o Are you getting everthing from several heiarchies?
Use wildcards instead! Fewer searches mean faster conversion.
Ie,
= sac.general
= sac.swap
= sac.test
and
+ sac.*
are equivalent. The second example is slightly faster, even though
it has to check a wildcard, because it has fewer lines to buffer
through and check.
o Even though "+ newsgroup.name" and "= newsgroup.name"
are (roughly) the same, use the "= newsgroup.name" method instead
when possible. The "+" syntax tells GIGO to keep checking,
for other mappings that might be more suitable. The "=" syntax says,
'hey, we've got the one we want, stop checking!'.
o Are you using wildcards at all? If you don't need them, but you
still have a large number of newsgroups (ie, 100+), you can
benefit by trading in features to get speed instead.
1: Add "FASTLOOKUP" to the top of mapping.cfg on a line by itself.
2: Make sure all lines are like this:
= alt.newsgroup.name ALT.ECHOMAIL.NAME
(It _is_ okay to use "@" mapping.cfg entries - but you _have_ to
give up "!", "+", and "-", for this speedup to work, since it's
bypassing the mapping.cfg parser and instead using a super-fast
lookup routine).
Make sure you watch your gateway run - if you make mistakes,
GIGO will be less forgiving, since the parser will have
been removed for a significant part of the lookups!
For those of you technically inclined, it will be using
a Pratt-Boyer-Moore search algorithm.
On gigo.com's gateway, this option doubled my speed, for a gateway
running around 350 newsgroups. Your mileage may vary, worse
or better, mainly depending on what search strings are involved..
o If you are using PARTIAL-35 (Partial FSC-35), and don't really need
it, you can turn it off for a bit of a speed increase due to GIGO
not having to actually compare the fido header and the FSC-35 extentions.
(If you actually find this feature useful, however, it's well worth
the speed hit..)
o Turn off the video. NOVIDEO in the config, or /NOVIDEO on the command
line, will tell GIGO to turn off video output. The normal startup
screens will still be shown, but once the gateway actually
starts processing mail, the video gets turned off. My tests have
shown this to speed things up by about 25%. Do this _after_ you've
got the gateway up and running. Between this, and disabling your
logging, you can really speed things up.
o Don't use virtual memory unless you really need it!